Method and apparatus for determining MoCA beacon transmit power

ABSTRACT

Systems and methods for efficiently establishing beacon transmission power, for example in networks in which beacon transmission responsibility can be passed between nodes. As a non-limiting example, various aspects of the present disclosure provide systems and methods for establishing beacon transmission power in a node that has received beacon transmission responsibility in a network, for example by hand-off, failover, etc.

CROSS-REFERENCE TO RELATED APPLICATIONS/INCORPORATION BY REFERENCE

This patent application makes reference to, claims priority to andclaims benefit from U.S. Provisional Patent Application Ser. No.62/036,489, filed on Aug. 12, 2014, and titled “Method and Apparatus forDetermining MoCA Beacon Transmit Power,” the entire contents of whichare hereby incorporated herein by reference.

FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

[Not Applicable]

SEQUENCE LISTING

[Not Applicable]

MICROFICHE/COPYRIGHT REFERENCE

[Not Applicable]

BACKGROUND

Various communication networks, for example in networks in which beacontransmission responsibility can be passed between nodes, lack a methodand/or apparatus for efficiently establishing beacon transmission power.Limitations and disadvantages of conventional methods and systems forestablishing beacon transmission power will become apparent to one ofskill in the art, through comparison of such approaches with someaspects of the present methods and systems set forth in the remainder ofthis disclosure with reference to the drawings.

BRIEF DESCRIPTION OF SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 is a simplified illustration of an example home comprising a MoCAnetwork and nodes.

FIG. 2 is a logical block diagram of a network node in accordance withvarious aspects of the present disclosure.

FIG. 3 is a simplified block diagram of example circuitry used toimplement a network node, in accordance with various aspects of thepresent disclosure

FIG. 4 is a flow diagram of an example method for determining beacontransmission power, in accordance with various aspects of the presentdisclosure.

SUMMARY

Various aspects of this disclosure provide systems and methods forefficiently establishing beacon transmission power, for example innetworks in which beacon transmission responsibility can be passedbetween nodes. As a non-limiting example, various aspects of the presentdisclosure provide systems and methods for establishing beacontransmission power in a node that has received beacon transmissionresponsibility in a network, for example by hand-off, failover, etc.

DETAILED DESCRIPTION OF VARIOUS ASPECTS OF THE DISCLOSURE

As utilized herein the terms “circuits” and “circuitry” refer tophysical electronic components (i.e., hardware) and any software and/orfirmware (“code”) that may configure the hardware, be executed by thehardware, and or otherwise be associated with the hardware. As usedherein, for example, a particular processor and memory (e.g., a volatileor non-volatile memory device, a general computer-readable medium, etc.)may comprise a first “circuit” when executing a first one or more linesof code and may comprise a second “circuit” when executing a second oneor more lines of code.

As utilized herein, circuitry is “operable” to perform a functionwhenever the circuitry comprises the necessary hardware and code (if anyis necessary) to perform the function, regardless of whether performanceof the function is disabled, or not enabled (e.g., by auser-configurable setting, factory setting or trim, etc.).

As utilized herein, “and/or” means any one or more of the items in thelist joined by “and/or”. As an example, “x and/or y” means any elementof the three-element set {(x), (y), (x, y)}. That is, “x and/or y” means“one or both of x and y.” As another example, “x, y, and/or z” means anyelement of the seven-element set {(x), (y), (z), (x, y), (x, z), (y, z),(x, y, z)}. That is, “x, y, and/or x” means “one or more of x, y, andz.” As utilized herein, the terms “e.g.,” and “for example” set offlists of one or more non-limiting examples, instances, or illustrations.

The terminology used herein is for the purpose of describing particularexamples only and is not intended to be limiting of the disclosure. Asused herein, the singular forms are intended to include the plural formsas well, unless the context clearly indicates otherwise. It will befurther understood that the terms “comprises,” “includes,” “comprising,”“including,” “has,” “have,” “having,” and the like when used in thisspecification, specify the presence of stated features, integers, steps,operations, elements, and/or components, but do not preclude thepresence or addition of one or more other features, integers, steps,operations, elements, components, and/or groups thereof.

It will be understood that, although the terms first, second, etc. maybe used herein to describe various elements, these elements should notbe limited by these terms. These terms are only used to distinguish oneelement from another element. Thus, for example, a first element, afirst component or a first section discussed below could be termed asecond element, a second component or a second section without departingfrom the teachings of the present disclosure. Similarly, various spatialterms, such as “upper,” “lower,” “side,” and the like, may be used indistinguishing one element from another element in a relative manner. Itshould be understood, however, that components may be oriented indifferent manners, for example a semiconductor device may be turnedsideways so that its “top” surface is facing horizontally and its “side”surface is facing vertically, without departing from the teachings ofthe present disclosure.

A premises (e.g., a home, office, campus, etc.) may comprise acommunication network for the sharing of information between variousdevices within the premises. For example, entertainment content may bereceived through a wide area network (WAN) provided by an MSO(Multi-system Operator), such as a cable television operator orsatellite content provider. Content provided to the premises may bedistributed throughout the premises over a premises-based network (e.g.,a home entertainment network, general premises-based communicationnetwork, etc.). The premises-based network may, for example, comprise alocal area network (LAN) in any of a variety of configurations, such asa mesh network. An example protocol for establishing a premises-basednetwork, for example a home entertainment LAN, is defined by thewell-known MoCA (Multi-media over Coax Alliance) network protocol thatis in-use today.

FIG. 1 is a simplified illustration of an example home 100 comprising aMoCA network 106 and nodes 110, 112, 114, and 116. Though only fournodes are illustrated it should be understood that the network 106 maycomprise any number of nodes. The nodes of the network 106 are coupledto a coaxial cable medium 128. In the example network 106, the signalspresent on the coaxial cables of the network 106 are available to eachof the nodes 110, 112, 114, and 116. A point of entry (POE) device 130allows selected information from outside the home to be coupled to thecoaxial medium 128 while preventing information that is intended toremain within the network 106 from flowing out. Though much of thediscussion herein presents examples of various aspects of the disclosurein the context of a MoCA network, it would be understood that the scopeof this disclosure is not limited to a MoCA network nor by variouscharacteristics of a MoCA network.

The example network 106, for example a MoCA network, may be formed byeach node, upon connecting to the medium 128, searching for another nodeto determine whether a network already exists. A New Node (NN) 118searches by attempting to detect the transmission of a Beacon message. ABeacon message may, for example, comprise an unencrypted transmissionsent by a node 110 operating as Network Coordinator (NC) (or networkcontroller). The NC 110 may, for example, be responsible for schedulingall of the activity on the network 106 over the coaxial medium 128. Allactivity on the network may, for example, be scheduled by the NC 110transmitting a Media Access Plan (MAP) message. In one exampleimplementation, there is always one, and only one, NC 110 on the network106 at a time. In an example implementation, any node of the network 106(e.g., a MoCA network) can assume responsibility for functioning as theNC. If there is no other network yet formed on the medium 128, the node110 will take on the responsibility for functioning as the NC and admitother nodes to form a network.

As other nodes are installed, they will each detect the Beacons beingtransmitted by this first node acting as the NC 110. When an NN 118detects the Beacons, the NN 118 will go through an admission processwhereby the NN 118 will gain admission to the network 106 established bythe NC 110. At times, if the NC 110 ceases functioning correctly, handsoff NC responsibility, or is removed from the network, responsibilityfor performing the functions of the NC will be taken up by another node(e.g., node 112) in the network 106.

In an example implementation, the NC 110 may for example establish theamount of power with which to transmit the Beacon signals over thecoaxial medium 128 by reading a control parameter that determines a“back-off” value. The power to be used is specified as the maximum powerminus the back-off (e.g., a specific amount of attenuation from themaximum power level). It should be understood, though, that the NC 110may determine a transmission power in any of a variety of manners, andthat the scope of the present disclosure is not limited bycharacteristics of any particular manner.

When an NC 110 is removed from service or hands off the NC role (orresponsibilities), a procedure is implemented to smoothly transition theNC responsibilities to another node. At a transition point, the new NC112 will then start to transmit the Beacons. In an exampleimplementation, the new NC 112 may read a control parameter associatedwith that node and determine the back-off value to be used by the NC 112in transmitting the Beacons. The new NC 112 will then transmit theBeacon at maximum power minus the back-off specified by the controlparameter maintained by the new NC 112. In this example, however, aproblem may arise, in that the maximum power of the new NC 112 might notbe the same as the maximum power of the previous NC 110. Therefore, itis not always desirable for the new NC 112 to assume the same back-offthat the previous NC 110 used when transmitting the Beacons. Inaddition, the new NC 112 may use a different back-off control parameterthan the control parameter used by the previous NC.

Accordingly, various aspects of the present disclosure provide systems,methods, and/or protocols that can establish the Beacon transmit powerfor a new network coordinator (NC) node quickly and effectively suchthat the Beacons will be transmitted by the new NC node at essentiallythe same power as they were being transmitted by the previous networkcoordinator.

Various aspects of the present disclosure provide systems and methodsthat allow a node that is to take over the role of Network Coordinator(NC) to determine the amount of power with which to transmit Beaconsover the network. Several example control parameters are presentedherein that control the process for setting the Beacon transmissionpower. An example Beacon Power Protocol Information Element (PIE) isalso presented herein, which provides for information regarding thevalues of these example control parameters to be shared and sentproperly through the network. In accordance with one exampleimplementation, a hierarchy is established for determining the amount ofpower that an NC is to use for transmitting Beacons over the network.

In one example implementation, a node may maintain a local variable, forexample named “Target Beacon Power.” A first example control parameterBEACON_PWR_(CFG) _(_) _(ONLY) may, for example, indicate whether an NCis to set its Target Beacon Power to a level determined by a secondcontrol parameter BEACON_PWR_(TX). In accordance with one exampleimplementation, if the value of the control parameter BEACON_PWR_(CFG)_(_) _(ONLY) is ENABLED, then the NC sets the value of the localvariable Target Beacon Power to the value indicated by the controlparameter BEACON_PWR_(TX).

Continuing the example, if the value of the control parameterBEACON_PWR_(CFG) _(_) _(ONLY) is DISABLED, then the node checks whethera Beacon Power PIE has been received since the node joined the network.If so, the node will set the value of the local variable Target BeaconPower to a value sent in the BEACON_TRANSMIT_POWER field of the receivedBeacon Power PIE. If the node has not received a Beacon Power PIE sincejoining the network, but had received a Beacon Power PIE before joiningthe network, then the node will check whether the value in aBEACON_POWER_PERSISTENCY field within the Beacon Power PIE was set to apredetermined value. If so, then the node will set the Target BeaconPower to the value indicated in the BEACON_TRANSMIT_POWER field of theBeacon Power PIE previously received. Otherwise, the node will set thevalue of the variable Target Beacon Power to the value of the controlparameter BEACON_PWR_(TX).

In addition, a control parameter BEACON_PWR_(DIST) is presented thatspecifies whether an NC is to send a Beacon Power PIE. If the controlparameter BEACON_PWR_(DIST) has a value of ENABLE, then the NC sends theBeacon Power PIE following any of at least three example events. A firstexample event is when a New Node completes admission. A second exampleevent is when a node becomes an NC after NC handoff or failover. A thirdexample event is when the variable Target Beacon Power changes due to anew BEACON_PWR_(TX) setting. Note that the scope of this disclosure isnot limited by characteristics of particular example events.

Further, an example control parameter HANDOFF_TO_LOWER_VER_(EN) ispresented herein, which restricts the ability of a node to assume and/orhandover the role of NC for the network.

FIG. 2 is a logical block diagram 200 of a network node 201 inaccordance with various aspects of the present disclosure. The networknode 201 may, for example, be operable to perform any or all of the nodefunctionality discussed herein (e.g., for a new node 118, networkcoordinator node 110, existing node 112, 114, and 116, any or all of thenodes discussed herein, etc.). In general, each node discussed hereinmay be functioning in a manner that is appropriate to the role such nodeis currently performing. For example, in the scenario illustrated inFIG. 1 and discussed herein, the NC node 110 performs the role of thenetwork NC, the node 118 plays the role of an NN that has not yet beenadmitted to the network 106, the Existing Nodes (EN) 112, 114, and 116play the role of a node that has been admitted to the network 106 by theNC 110, etc. In various example scenarios discussed herein, the EN 112may also play the roll of a node that is in the process of taking overNC functionality from the NC node 110. Various functions of the networknodes are disclosed herein in order to understand how each nodefunctions in its role in accordance with various aspects of the presentdisclosure.

The example node 201 uses the seven layer Open System Interconnection(OSI) model and/or any generally analogous layered communication model.For example, the node 201 may comprise circuitry that operates toimplement a physical layer 202 which is responsible for controlling thephysical interface to the medium (e.g., cable medium, phone line medium,other wired medium, wireless medium, tethered and/or untethered opticalmedium, etc.), including transmitting and/or receiving signals over themedium.

The node 201 may comprise circuitry that operates to implement a DataLink Layer (DLL) 204, for example comprising several sub-layers (e.g.,an Ethernet Convergence Layer (ECL) 206, Link Layer Control (LLC) 208,Media Access Control (MAC) 210, etc.). The DLL 204 may, for example, beresponsible for controlling the higher layer operation above thephysical layer and determining the timing and management of messages tobe transmitted and received. Accordingly, the DLL 204 may work with thephysical layer 202 to perform any or all of the functions discussedherein (e.g., with regard to FIGS. 1-4). In one example implementation,the DLL 204 is implemented by the execution of software running on atleast one processor. The DLL 204 and/or any of the layers shown in FIG.2 may be implemented by any of a variety of types of processingcircuitry (e.g., application-specific integrated circuitry, programmablearray logic circuitry, discrete logic circuitry, general-purposeprocessor circuitry, specific-purpose processing circuitry, etc.).

In accordance with various aspects of the present disclosure, aManagement Entity (ME) 214 may, for example, comprise a high layerlogical device associated with the node 201. The ME 214 or portionsthereof may, for example, be collocated with the node 201 and/or may beimplemented at a location that is geographically remote from the node201. The ME 214, for example, uses the node 201 to send and receiveinformation over the network.

FIG. 3 is a simplified block diagram of example circuitry used toimplement a network node 300, in accordance with various aspects of thepresent disclosure. The network node 300 may, for example, be operableto perform any or all of the node functionality discussed herein (e.g.,with regard to FIGS. 1-4). The network node 300 may, for example, shareany or all characteristics with any of the nodes discussed herein (e.g.,the node 201 of FIG. 2, the nodes 110, 112, 114, 116, and 118 of FIG. 1,etc.).

The node 300 comprises at least one processor 301, a memory 302, and aPHY 304. The memory 302 is coupled to the processor 301. The PHY 304includes an RF front end 306. The PHY 304 may also include a dedicatedprocessor (not shown) that performs functions associated with the PHY304. Alternatively, some control functions of the PHY 304 may beperformed by the processor 301. In the transmit path, the PHY 304 and/orRF Front End 306 may receive information from the processor 301. Theinformation is modulated on signals generated by the RF front end 306.The RF front end 306 transmits such signals over a medium 128 (e.g.,over coaxial cabling used to connect notes of a MoCA network, etc.). Inthe receive path, the PHY 304 and/or RF front end 306 receive signalsfrom the medium 128, demodulates the signals to retrieve the informationcommunicated by such signals, and passes the received information to theprocessor 301 for processing. It should be understood that, while theexample node 300 shown in FIG. 3 (and other nodes discussed herein) isdescribed with respect to a node connected to a network via coaxialcable, the node 300 may be connected to the network over any medium.

The processor 301 within the node 300 performs several tasks. Theexample node 300 is shown and described as having a single processor 301that performs all of the disclosed tasks and functions of the node 300.Nonetheless, it should be understood that the disclosed tasks andfunctions of the node 300 may be performed by any combination ofhardware, firmware, and software. Furthermore, any software or firmwaremay be executed by one or a combination of several independent orcoordinated processors. For example, in various example implementations,it may be more efficient to use processors dedicated to performing aparticular task or group of tasks. Also for example, the processor 301(or processors) may comprise any of a variety of processing circuits(e.g., general purpose processors, specific purposes processors,microcontrollers, application-specific integrated circuits, programmablestate machine devices, analog and/or digital circuitry, etc.). In analternative implementation, the node 300 may have several processorsthat work together or independently. The processor 301 may, for example,read computer readable program code from the memory 302 and execute thecode to perform the functions of the DLL 204, the upper layers 212and/or the ME 214 (see FIG. 2). In one example implementation, the ME214 is not co-located with the DLL 204. In such an exampleimplementation, the ME 214 may be implemented using a differentprocessor or processors. Likewise, in one example implementation, theupper layers 212 are not co-located with the DLL 204. It should beunderstood that the particular physical layout of the logical componentsmay vary substantially, so long as the disclosed functionality may beperformed. In an alternative implementation, the functions of the DLL204 and other functions disclosed herein may be performed by dedicatedhardware, firmware or a combination of hardware, firmware and softwareexecuted by a special or general purpose processor.

In accordance with various aspects of the present disclosure, at leastthe following five example control parameters indicated in Table 1 aremaintained in addition to other control parameters not noted herein andused by nodes of the network, for example operating in accordance any ofa variety of network protocols (e.g., the MoCA protocol).

TABLE 1 Control Parameters Associated with Beacon Tx Power ParameterName Description Values BEACON_PWR_(CFG) _(—) _(ONLY) Controls whetherthe Node ENABLED, DISABLED only uses the BEACON_PWR_(TX) and ignores theBeacon transmit power distributed by the NC BEACON_PWR_(DIST) Controlswhether the Node ENABLED, DISABLED distributes its BEACON_PWR_(TX) toother Nodes when being the NC BEACON_PWR_(PERSISTENCY) Controls whetherother Nodes ENABLED, DISABLED are required to persistently use thedistributed Beacon transmit power and ignore its own managed parameterBEACON_PWR_(TX) even after the transmitting node drops from the networkBEACON_PWR_(TX) The value of Beacon transmit Any integer in range powerin units of dBm of −10 to +7 HANDOFF_TO_LOWER_VER_(EN) Controls whetherhandoff to a ENABLED, DISABLED MoCA 2.0 or MoCA 1 node is enabled ordisabled

The first column of Table 1 indicates the name of the example controlparameter. The second column provides a description of the examplecontrol parameter. The third column indicates permissible values for theexample control parameter. It should be understood that the examplecontrol parameter names and example descriptions are merely examples,and thus the scope of this disclosure is not limited by such examplecontrol parameter names and/or example control parameter descriptions.

The first example control parameter in Table 1 is BEACON_PWR_(CFG) _(_)_(ONLY). The value of this example control parameter indicates whether anode 112, which for example is to become the NC, is to use only thevalue provided in the control parameter BEACON_PWR_(TX) to determine thepower level at which to transmit Beacons. If BEACON_PWR_(CFG) _(_)_(ONLY) carries a value of “ENABLE”, then the node 112 will ignore allBeacon power information provided by the previous NC 110. In accordancewith one example implementation, the node 112 transmits the Beacons at alevel indicated by a local variable Target Beacon Power.

The second example control parameter is BEACON_PWR_(DIST). The value ofthis example control parameter determines whether the node 110distributes the value held in the local variable Target Beacon Power toother nodes 112, 114, 116 in the network 106 when operating as the NC.When the value of this control parameter is “ENABLE”, the node 110 willdistribute the value of Target Beacon Power to other nodes as discussedherein.

The third example control parameter is BEACON_PWR_(PERSISTENCY). If thevalue of this example control parameter is “ENABLE”, the node 110requires that the other nodes 112, 114, 116 of the network 106 continueto use the Beacon transmit power value provided by the node 110, evenfor example after the node 110 ceases to function as the NC or leavesthe network 106.

The fourth example control parameter is BEACON_PWR_(TX). This examplecontrol parameter carries an integer value that indicates (e.g., in dBm)the power with which the node 110 is to transmit Beacons when the node110 is operating as the NC. In accordance with one exampleimplementation, the value of the control parameter BEACON_PWR_(TX) is ina range between −10 dBm and +7 dBm.

The fifth example control parameter is HANDOFF_TO_LOWER_VER_(EN). Thisexample control parameter controls whether a handoff of theresponsibility for performing the NC functions can be made to a nodethat operates in accordance with an older version of the networkprotocol. In accordance with one example implementation, this examplecontrol parameter is used to control whether the node 110 (e.g.,operating in accordance with MoCA 2.1) can hand off responsibility forperforming the functions of the NC to a MoCA 2.0 or MoCA 1 node.

In accordance with various aspects of the present disclosure, an exampleInformation Element (IE) is provided in Table 2. The IE allows a node110 that is operating as the NC for a network 106 to provide informationto the other nodes 112, 114, 116 of the network 106. For example, the IEallows the node to indicate the power level to be used to transmitBeacons if one of the other nodes 112, 114, and 116 were to assumeresponsibility for operating as the NC.

TABLE 2 Beacon Power Protocol Information Element Format Field LengthUsage Protocol IE Header FRAME_SUBTYPE 4 bits 0xC - Beacon Power IEFRAME_TYPE 4 bits 0x7 - Protocol IE IE_LENGTH 6 bits 0x00 RESERVED 2bits Type III Protocol IE Payload RESERVED 10 bits  Type IIIBEACON_POWER_PERSISTENCY 1 bit  Indicates whether the NC enforces theother Nodes to persistently use the BEACON_TRANSMIT_POWER in this PIEfor Beacon transmissions. The field MUST be set to 1 ifBEACON_PWR_(PERSISTENCY) = ENABLED and 0 if BEACON_PWR_(PERSISTENCY) =DISABLED. BEACON_TRANSMIT_POWER 5 bits Two's complement integer value ofthe Target Beacon Power in units of dBm. The Target Beacon Power isdefined as Section 7.1.1

It should be understood that the example information element name,example field names and example field descriptions are merely examples,and thus the scope of this disclosure is not limited by such examples.

When a node (e.g., the network coordinator node 110, any other nodediscussed herein, etc.) determines that it is to take responsibility forperforming the functions of the NC for the network 106, the node 110must determine the power level at which to transmit Beacons. An examplemanner of making such a determination is provided at FIG. 4. It shouldbe understood that the scope of this disclosure is not limited by anyspecific characteristics of the example method illustrated by FIG. 4,which merely provides examples of various aspects of the disclosure.

FIG. 4 is a flow diagram of an example method 400 for determining beacontransmission power, in accordance with various aspects of the presentdisclosure. For example, a node (e.g., any of the nodes discussedherein) assuming and/or having a network coordinator role may operate inaccordance with the example method 400, or any portion thereof, todetermine the transmission power utilized for transmission of a Beacon.In an example implementation, a value of at least one local parameter ofthe node (e.g., Target Beacon Power) determines the power level at whichthe node 110 transmits Beacons.

In accordance with one example implementation, the example method 400begins execution at block 401, at which a node begins to (or anticipatesbeginning to) transmit Beacons. For example, in one exampleimplementation, a node 110 needs to transmit Beacons whenever it isoperating as an NC.

At flow control block 403, the node 110 checks the status of theBEACON_PWR_(CFG) _(_) _(ONLY) control parameter. If the BEACON_PWR_(CFG)_(_) _(ONLY) is ENABLED, then the flow control block 403 directsexecution of the example method 400 to block 405, at which the node 110will set its Target Beacon Power to the value BEACON_PWR_(TX) and begintransmitting beacons at the power level indicated by the Target BeaconPower. If, however, the BEACON_PWR_(CFG) _(_) _(ONLY) is not ENABLED,then the flow control block 403 directs execution flow of the examplemethod 400 to block 407, at which the node 110 determines whether aBeacon Power Protocol IE (PIE) has been received since the node 110joined the network 106.

If a Beacon Power PIE has been received since the node 110 joined thenetwork 106, then the flow control block 407 directs execution flow ofthe example method 400 to block 409, at which the node 110 will set theTarget Beacon Power to the value that was received in theBEACON_TRANSMIT_POWER field of the last received Beacon Power PIE. If,however, the node 110 has not received a Beacon Power PIE since joiningthe network 106, then the flow control block 407 directs execution flowof the example method 400 to block 411, at which the node 110 determineswhether the node 110 had received a Beacon Power PIE prior to joiningthe network 106.

If the node 110 has received a Beacon Power PIE prior to joining thenetwork 106, then the flow control block 411 directs execution flow ofthe example method 400 to block 413, at which the node 110 will checkwhether the BEACON_POWER_PERSISTENCY in its last received Beacon PowerPIE was set to ENABLE. As noted in Table 2, such a value of ENABLE may,for example, indicates that the node from which the Beacon Power PIE wassent requires that all receiving nodes remain “persistent” (e.g.,continue to use the value indicated in the BEACON_TRANSMIT_POWER field,even after the transmitting node leaves the network).

If persistence was enabled in the transmitting node, then the flowcontrol block 413 will direct execution flow of the example method 400to block 415, at which the receiving node 110 will set the Target BeaconPower to the value of the BEACON_TRANSMIT_POWER field of the lastreceived Beacon Power PIE and transmit beacons at the Target BeaconPower level. If, however, persistence was not enabled in thetransmitting node, then flow control block 413 will direct executionflow of the example method 400 to block 405, discussed above.

In one example implementation, either a user or a management entity 214associated with an NC 110 can write a value to the example controlparameter BEACON_POWER_(TX). In accordance with one exampleimplementation, when either the user or the management entity 214changes the value of the Beacon transmit power, the NC 110 changes theBeacon transmit power in monotonic steps of 1 dB per Beacon untilreaching the level indicated by the new value of BEACON_POWER_(TX).

An NC 110 may transmit a Beacon Power PIE in response to any of avariety of causes or conditions, non-limiting examples are providedherein. For example, if the example control parameterBEACON_POWER_(DIST) is set to ENABLE, and any of the following eventsoccur, then the NC 110 must transmit a Beacon Power PIE:

-   -   The first example event occurs when a New Node (NN) 118        completes an admission to the network 106. In accordance with        one example implementation, this can be determined by a change        from “Begin PHY Profile State” to “Steady State” of the        LINK_STATE_II in MAPs transmitted by the NC 110.    -   The second example event occurs when a node becomes an NC after        NC handoff or “failover” (e.g., when it is determined that an NC        110 has failed and another node 112 is required to take over        responsibility for the NC functions for the network 106).    -   The third example event occurs when the value of the Local        Variable Target Beacon Power changes due to a new value for        BEACON_PWR_(TX).

In accordance with one example implementation, when any of these threeevents occur, the NC sends the Beacon Power PIE three different times.The first time, the Beacon Power PIE is sent in a first MAP messagewithin Beacon cycles 1 to 3 following the event. The second time, theBeacon PIE is sent in a second MAP message within Beacon cycles 4 to 6following the event. The third time, the Beacon PIE is sent in a thirdMAP message within Beacon cycles 7 to 9 following the event.

In accordance with one example implementation, in order to ensure thateach node that might take on the responsibility of performing the NCfunctions for the network is capable of performing the desired NCfunctions, the control parameter HANDOFF_TO_LOWER_VER_(EN) can be set toprevent a node that does not have the ability to perform the disclosedmethod from receiving an NC handoff.

In summary, various aspects of this disclosure provide systems andmethods for efficiently establishing beacon transmission power, forexample in networks in which beacon transmission responsibility can bepassed between nodes. While the foregoing has been described withreference to certain aspects and examples, it will be understood bythose skilled in the art that various changes may be made andequivalents may be substituted without departing from the scope of thedisclosure. In addition, many modifications may be made to adapt aparticular situation or material to the teachings of the disclosurewithout departing from its scope. Therefore, it is intended that thedisclosure not be limited to the particular example(s) disclosed, butthat the disclosure will include all examples falling within the scopeof the appended claims.

The invention claimed is:
 1. A network comprising: a first network node;and a network coordinator node, wherein: the network coordinator nodecomprises at least one circuit operable to, at least: analyze at least afirst beacon power control parameter to determine whether to distributea beacon power value to one or more other nodes of the network; and ifit is determined to distribute the beacon power value to one or moreother nodes of the network, then at least: populate a beacon powerinformation element with information comprising the beacon power value;and transmit the beacon power information element in a broadcastmessage; and the first network node comprises at least one circuitoperable to, at least: analyze at least a second beacon power controlparameter to determine whether to utilize the distributed beacon powervalue or a local beacon power value for transmission of a beacon; if itis determined to utilize the distributed beacon power value fortransmission of the beacon, then transmit the beacon with a transmissionpower that is in accordance with the distributed beacon power value; andif it is determined to utilize the local beacon power value fortransmission of the beacon, then transmit the beacon with a transmissionpower that is in accordance with the local beacon power value.
 2. Thenetwork of claim 1, wherein the broadcast message is a Media Access Plan(MAP) message.
 3. The network of claim 1, wherein the at least onecircuit of the first network node is operable to store a plurality ofcontrol parameters in a memory, wherein: the control parameters comprisethe second beacon power control parameter; and the second beacon powercontrol parameter indicates whether the first network node is totransmit beacons in accordance with a power value that is distributed tonetwork nodes.
 4. The network node of claim 1, wherein the at least onecircuit of the network coordinator node is operable to, when it isdetermined to transmit the beacon power information element in abroadcast message, always transmit the beacon power information elementin a broadcast message at least three times, each in a differentrespective Media Access Control (MAP) message and in a differentrespective beacon cycle.
 5. A network node comprising: at least onecircuit comprising a processor, memory, and communication mediuminterface circuitry, wherein the at least one circuit is operable to, atleast: analyze at least a first beacon power control parameter todetermine whether to utilize a distributed beacon power value that isdistributed by a network coordinator or to utilize a local beacon powervalue for transmission of a beacon; if it is determined to utilize thedistributed beacon power value for transmission of the beacon, thentransmit the beacon with a transmission power that is in accordance withthe distributed beacon power value; and if it is determined to utilizethe local beacon power value for transmission of the beacon, thentransmit the beacon with a transmission power that is in accordance withthe local beacon power value.
 6. The network node of claim 5, whereinthe at least one circuit is operable to set a second beacon powercontrol parameter to the distributed beacon power value.
 7. The networknode of claim 5, wherein the at least one circuit is operable to receivethe distributed beacon power value in a beacon power information elementtransmitted by a network coordinator node.
 8. The network node of claim5, wherein the at least one circuit is operable to receive thedistributed beacon power value in a beacon power information element ofa Media Access Plan (MAP) message transmitted by a network coordinatornode, the beacon power information element comprising: a headercomprising a first field that identifies the beacon power informationelement as a beacon power information element; and a payload comprisinga second field that comprises the distributed beacon power value.
 9. Thenetwork node of claim 8, wherein the payload of the beacon powerinformation element comprises a third field that identifies thedistributed beacon power value as a network-wide beacon transmit power.10. The network node of claim 5, wherein the at least one circuit isoperable to store a plurality of control parameters in a memory,wherein: the control parameters comprise the first beacon power controlparameter; and the first beacon power control parameter indicateswhether the network node is to transmit beacons in accordance with apower value that is distributed to network nodes.
 11. The network nodeof claim 5, wherein the at least one circuit is operable to store aplurality of control parameters in a memory, the control parameterscomprising a second beacon power control parameter that indicates atarget beacon transmission power.
 12. The network node of claim 11,wherein the second beacon power control parameter is settable by amanagement entity logically associated with the network node and/or auser.
 13. The network node of claim 12, wherein the at least one circuitis operable to, in response to a change in the second beacon powercontrol parameter, change beacon transmission power monotonically insteps of 1 dB per beacon.
 14. The network node of claim 5, wherein theat least one circuit is operable to store a plurality of controlparameters in a memory, the control parameters comprising a beacon powerdistribution control parameter that indicates whether the network nodeis to distribute its beacon transmission power level to other nodes. 15.The network node of claim 5, wherein the at least one circuit isoperable to store a plurality of control parameters in a memory, thecontrol parameters comprising a handoff control parameter that indicateswhether the network node may hand off network coordinator functionalityto another node operating in accordance with an earlier version of astandard that the network node is operating in accordance with.
 16. Anetwork node comprising: at least one circuit comprising a processor,memory, and communication medium interface circuitry, wherein the atleast one circuit is operable to, at least: analyze at least a firstbeacon power control parameter to determine whether to control beacontransmission power of one or more other nodes of a network; and if it isdetermined to control the beacon transmission power of the one or moreother nodes of the network, then at least: populate a beacon powerinformation element with information comprising a beacon power value;and transmit the beacon power information element in a broadcastmessage.
 17. The network node of claim 16, wherein the network node is anetwork coordinator node of a premises-based coaxial cable communicationnetwork.
 18. The network node of claim 16, wherein the broadcast messageis a Media Access Plan (MAP) message comprising medium access scheduleinformation.
 19. The network node of claim 16, wherein the at least onecircuit is operable to, when it is determined to transmit the beaconpower information element in a broadcast message, always transmit thebeacon power information element in a broadcast message at least threetimes, each in a different respective Media Access Control (MAP)message.
 20. The network node of claim 16, wherein the at least onecircuit is operable to, when it is determined to transmit the beaconpower information element in a broadcast message, always transmit thebeacon power information element in a broadcast message at least threetimes, each in a different respective beacon cycle.
 21. The network nodeof claim 16, wherein the at least one circuit is operable to determinewhether to control beacon transmission power of one or more other nodesof the network based, at least in part, on a determination that a newnode has completed admission to the network and on a beacon powercontrol parameter independent of present communication mediumconditions, that indicates the beacon power value is to be distributed.22. The network node of claim 16, wherein the at least one circuit isoperable to determine whether to control beacon transmission power ofone or more other nodes of the network based, at least in part, on adetermination that another node is taking over network coordinatoroperation for the network and on a beacon power control parameter,independent of present communication medium conditions, that indicatesthe beacon power value is to be distributed.
 23. The network node ofclaim 16, wherein the at least one circuit is operable to determinewhether to control beacon transmission power of one or more other nodesof the network based, at least in part, on a beacon transmit powercontrol parameter of the network node being modified, and on a beaconpower control parameter, independent of present communication mediumconditions, that indicates the beacon power value is to be distributed.24. The network node of claim 16, wherein the at least one circuit isoperable to determine whether to control beacon transmission power ofone or more other nodes of the network based, at least in part, on abeacon transmit power control parameter, independent of presentcommunication medium conditions, of the network node being modified by amanagement entity logically associated with the network node.